CVE-2026-12053
Insertion of Sensitive Information into Log File in GitLab
Description
GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.1 that under certain conditions could have allowed a user to access sensitive information that had already been committed to a project, due to insufficient output filtering in Duo Workflows.
INFO
Published Date :
June 25, 2026, 4:33 a.m.
Last Modified :
June 25, 2026, 4:33 a.m.
Remotely Exploit :
Yes !
Source :
GitLab
Affected Products
The following products are affected by CVE-2026-12053
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | ceab7361-8a18-47b1-92ba-4d7d25f6715a | ||||
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Update GitLab EE to 19.1.1 or later.
- Apply vendor patches and updates promptly.
- Review output filtering for sensitive data.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-12053 vulnerability anywhere in the article.